Skip to content

ci: update GitHub Actions to latest versions#78

Merged
Kav91 merged 5 commits into
mainfrom
kav/updateWf2
Jul 14, 2026
Merged

ci: update GitHub Actions to latest versions#78
Kav91 merged 5 commits into
mainfrom
kav/updateWf2

Conversation

@Kav91

@Kav91 Kav91 commented Jul 14, 2026

Copy link
Copy Markdown
Member

Bump actions/checkout v2->v4, actions/setup-node v1->v4, and actions/cache v1->v4. Add persist-credentials: false to checkouts and modernize cache key config.

Kav91 added 5 commits July 14, 2026 09:09
Bump actions/checkout v2->v4, actions/setup-node v1->v4, and
actions/cache v1->v4. Add persist-credentials: false to checkouts
and modernize cache key config.
react-select@^3.2.0 requires react >=16.8 but the project pins
react@16.6.3, which npm 7+ treats as a hard ERESOLVE error and
fails npm ci. Enable legacy-peer-deps to restore the prior
resolution behavior.
The lockfile had been regenerated at lockfileVersion 2, under which
npm 7+ strictly enforces peer deps and fails npm ci because
react-select@^3.2.0 wants react >=16.8 while the project pins
react@16.6.3. Regenerate as lockfileVersion 1 (matching the other
nerdpacks) so npm ci resolves without the conflict. Removes the
.npmrc legacy-peer-deps workaround.
react@16.6.3 failed react-select@^3.2.0's peer requirement
(react >=16.8), causing npm ci to fail with ERESOLVE under npm 7+.
Bump to ^16.14.0, the highest react 16 release, which satisfies all
peers (react-select, semantic-ui-react, react-virtualized). react 17
is not viable here because react-virtualized@9.22.2 caps react at 16.
Regenerated lockfile resolves cleanly without legacy-peer-deps.

@aso1124 aso1124 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Kav91 Kav91 merged commit 45d3431 into main Jul 14, 2026
13 checks passed
@nr-opensource-bot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.7.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants